Database Backup¶
To ensure uninterrupted access to passwords even in the unlikely event of a disaster, you can take a backup of the entire database and store it in a secure location. If something goes wrong with the existing installation, you can do a quick recovery of data. Backup can be taken anytime on-demand and at periodic intervals by creating a scheduled task.
Configuring Backup¶
To configure database backup, navigate to Admin >> High Availability >> Database Backup section in the GUI. There are two options to choose from when scheduling a backup. You can choose to take a backup once whenever required or at periodic intervals.
If you want to take a backup instantly, you can click on Backup Now. If you choose Take Backup Once, follow the steps below:
- Select the date and time when you want to take backup once.
- If needed, change the backup destination from its default location by providing the destination folder path. When the backup file is to be stored in another machine, you can specify the network path to that destination.
- Specify the maximum number of backups to be retained in that location. For example, if you specify this as 5, only the most recent 5 backup copies will be retained. Click Save
If you choose Take Backup Periodically’, follow the steps below to create a scheduled task:
- Choose the date and time of the first backup.
- Thereafter, you can schedule backups on an hourly, daily, weekly, and monthly basis. Choose an option between ‘Hours’, ‘Days’, ‘Weeks’, and ‘Months’ from the drop-down menu. Specify the number of hours/days/weeks/months in the adjacent space.
- If needed, change the backup destination from its default location by providing the destination folder path. When the backup file is to be stored in another machine, you can specify the network path to that destination.
- Specify the maximum number of backups to be retained in that location. For example, if you specify this as 5, only the most recent 5 backup copies will be retained.
- Click Save
Disabling the Database Backup¶
You can use the disable option to delete an already existing backup schedule along with its configurations.
Important
Every installation has a randomly generated, unique encryption key, using which sensitive data are encrypted and stored in the database. By default, the encryption key is located at
When you start the Securden server, the key should be available in the path specified every time. Otherwise, the server won't start, and you won't be able to access the passwords.
This encryption key is needed to restore the data from the backup copy. If you don’t have the encryption key, data cannot be restored. Ensure that you have a copy of the encryption key for disaster recovery.
Steps for Data Recovery¶
In the event of a disaster, you can restore the data and the configurations from a backup file.
Important
The backup data is encrypted using the same encryption key as the original. For data restoration, Securden requires access to the encryption key.
Ensure the key is available at the location specified in the current(new) installation of Securden. By default, the encryption key is located at
You can also identify the current location of the encryption key by navigating to Admin >> Security >> Change encryption key location, and hovering the pointer over the “i” icon (or) Open the file named Securden_key.location using a text editor. This file can be found at
To Recover the backed-up data, follow the steps below
- Install Securden in a new machine without disturbing the existing installation.
- Stop the Securden server.
- Open services.msc
- Navigate to Securden PAM Service.
- Stop the service.
- Open Command Prompt by clicking on ‘Run as Administrator’.
- Navigate to
/bin. - In the cmd window, use the following command.
- RestoreDatabase.exe
- Example: RestoreDatabase.exe C:\ProgramFiles\Securden\PAM\exports\PostgreSQL_Backups\Securden_postgresql_db_backup_2019-05-22-11-48-2.zip
- Start Securden PAM service from services.msc. (You can safely ignore the other service named Securden Web Service, which is automatically taken care of).